482.37.3 Priorities[//]

After selecting this menu option, an overview screen is displayed:

Options on the screen

New priority code: Use this option to add a new priority code. See section 482.37.3.1.

Modify priority code: Select a line and then this option to view / modify the details of an existing code. See section 482.37.3.1.

Delete priority code: Select a line and then this option to delete the selected code. The system will prompt for confirmation.

482.37.3.1 Add / modify codes[//]

After selecting the option New priority code or Modify priority code an input form will be displayed:

Fields on the screen

Priority code: A unique code identifying the priority.

Wording: A brief description of the code. This will appear in the Priority column in AFO 434 as well as in the dropdown list for assigning priorities in AFO 434.

Description: Additional information about the code that will only appear here.

Priority value: This field is for future use.

In use: To denote whether the code is currently in use or not.

Notes

·                Priority codes that are not in use cannot be attributed to incidents.

·                It is NOT mandatory to define these parameters. If no priorities are defined, the system will automatically attribute the priority 1 to an incident.

·                Default priorities can be linked to an Incident Type.

·                Priorities that are in use as the default priority for an Incident Type cannot be set to Not in use. Priorities that are attached to existing contact events can be set to Not in use.

·                The assumption is that 1 is the highest priority.

482.37.4 Types[//]

After selecting this menu option, an overview screen is displayed:

Options on the screen

New type code: Use this option to add a new type code. See section 482.37.4.1.

Modify type code: Select a line and then this option to view / modify the details of an existing code. See section 482.37.4.1.

Delete type code: Select a line and then this option to delete the selected code. The system will prompt for confirmation.

482.37.4.1 Add / modify codes[//]

After selecting the option New type code or Modify type code an input form will be displayed:

Fields on the screen

Type code: A unique code identifying the type.

Wording: A brief description of the code. This will appear in the Type column in AFO 434 as well as in the dropdown list for assigning priorities in AFO 434.

Description: Additional information about the code that will only appear here.

Priority: Select a default priority for the type from the dropdown list. This can be mdofied when assigning  the code in AFO 434.

Default due date (days): Enter a default due date for the type [the number of days that is defined as the period in which the incident should be closed].

Default due date event (days): Enter a default due date for an event attached to an incident of this type [the number of days that is defined as the period in which the event should be “closed” – the latter implies in fact that either the event is closed or a new (next) event is created].

In use: To denote whether the code is currently in use or not.

Notes

·                All properties, with the exception of the Type description, are mandatory.

·                Types that are not in use cannot be attributed to incidents.

·                To be able to work with the Contact incident management, at least one type that is in use must exist. If this is not the case, a message will appear in the management of contact incidents, pointing out that the system is not configured correctly.

482.37.5 Methods[//]

After selecting this menu option, an overview screen is displayed:

Options on the screen

New method code: Use this option to add a new method code. See section 482.37.5.1.

Modify method code: Select a line and then this option to view / modify the details of an existing code. See section 482.37.5.1.

Delete method code: Select a line and then this option to delete the selected code. The system will prompt for confirmation.

482.37.4.1 Add / modify codes[//]

After selecting the option New method code or Modify method code an input form will be displayed:

Fields on the screen

Contact method code: A unique code identifying the contact method.

Wording: A brief description of the code. This will appear in the Type column in AFO 434 as well as in the dropdown list for assigning types in AFO 434.

Description: Additional information about the code that will only appear here.

In use: To denote whether the code is currently in use or not.

Notes

·                Methods that are not in use cannot be attributed to incidents.

·                To be able to work with the Contact incident management, at least one method that is in use must exist. If this is not the case, a message will appear in the management of contact incidents, pointing out that the system is not configured correctly.

482.37.6 Triggers[//]

The following parameters are used by the trigger batch process. The trigger parameters are defined as rules. None, one or more rules can exist on a single system.

Each rule is defined for a combination of event type and receiver. The rule properties are linked to the type/receiver combination. These combinations define the scope of the rule and can have the following formats:

After selecting this menu option, an overview screen is displayed:

Options on the screen

New trigger code: Use this option to add a new trigger code. See section 482.37.6.1.

Modify trigger code: Select a line and then this option to view / modify the details of an existing code. See section 482.37.6.1.

Delete trigger code: Select a line and then this option to delete the selected code. The system will prompt for confirmation.

Execute triggers: Use this option to process the triggers. The system will swicth to the standard screen for executing processes.

482.37.4.1 Add / modify codes[//]

After selecting the option New trigger code or Modify trigger code an input form will be displayed:

Fields on the screen

Trigger code: A unique code identifying the trigger.

Scope: As described in the above table; the scope must be unique for the rule, i.e. the same scope can only be attached to a single rule, independent of the fact that the rule is or is not in use.

Report to: Select the required user name(s) from the list.

Report to incident owner: When this is checked the owner of the incident will be notified something needs to be done.

Report to next action owner: When this is checked the owner of the next action will be notified something needs to be done.

Timing: Trigger action timing [x1,x2,x3,…xm] [in which x[1:1:m] = -n:1:0:1:n].

Email: When this is checked the owners will be notified via email.

Description: Additional information about the code that will only appear here.

In use: To denote whether the code is currently in use or not.